Skip to content

Set ImageRenderMethodForWeb.HttpGet, as a default imageRenderMethodForWeb for flutter 3.27.0 compatibility workaround - #996

Open
rednikisfun wants to merge 2 commits into
Baseflow:mainfrom
Neotech-iHoops:develop
Open

rednikisfun wants to merge 2 commits into
Baseflow:mainfrom
Neotech-iHoops:develop

Conversation

@rednikisfun

Copy link
Copy Markdown

Set ImageRenderMethodForWeb.HttpGet, as a default imageRenderMethodForWeb for flutter 3.27.0 compatibility workaround

✨ What kind of change does this PR introduce? (Bug fix, feature, docs update...)

Workaround

⤵️ What is the current behavior?

Currently on flutter version 3.27.0, usage of cached_network_image causes canvaskit.js:21 Uncaught (in promise) SecurityError: Failed to execute 'texImage2D' on 'WebGL2RenderingContext': The image element contains cross-origin data, and may not be loaded. errors

🆕 What is the new behavior (if this is a feature change)?

Setting the ImageRenderMethodForWeb.HttpGet, as a default imageRenderMethodForWeb prevents the errors from being thrown, and the app doesn't crash.

💥 Does this PR introduce a breaking change?

Yes, the default value is being changed, which can cause unexpected behavior on older flutter versions

🐛 Recommendations for testing

📝 Links to relevant issues/docs

https://github.com/Baseflow/flutter_cached_network_image/issues/995
https://github.com/flutter/flutter/issues/160127

🤔 Checklist before submitting

  • [yes] All projects build
  • [yes] Follows style guide lines (code style guide)
  • [no] Relevant documentation was updated
  • [yes] Rebased onto current develop

Set` as a default `imageRenderMethodForWeb` for flutter 3.27.0 compatibility workaround
@AndreiMisiukevich

Copy link
Copy Markdown

ImageRenderMethodForWeb.HttpGet has significant performance issues, especially with a list of images.
I believe the proper fix should be in the Flutter repo (where it was broken).

@rickdijk

Copy link
Copy Markdown
Collaborator

This repository now uses main as its only branch, so I have retargeted this PR from develop to main. Nothing about the review changes. If GitHub now shows a conflict, a rebase onto main will clear it, and we will follow up on that separately.

@rickdijk
rickdijk changed the base branch from develop to main September 23, 2026 17:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants